chore(main): release 6.3.0#949
Conversation
|
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final This is an automated message from the Argus AI review workflow. |
|
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final This is an automated message from the Argus AI review workflow. |
|
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final This is an automated message from the Argus AI review workflow. |
|
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final This is an automated message from the Argus AI review workflow. |
aao-ipr-bot
Bot
force-pushed
the
release-please--branches--main--components--adcp
branch
from
288f497 to
eb8d1f2
Compare
|
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final This is an automated message from the Argus AI review workflow. |
|
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final This is an automated message from the Argus AI review workflow. |
aao-ipr-bot
Bot
force-pushed
the
release-please--branches--main--components--adcp
branch
from
1812cbc to
5571964
Compare
|
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final This is an automated message from the Argus AI review workflow. |
|
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final This is an automated message from the Argus AI review workflow. |
bokelley
force-pushed
the
release-please--branches--main--components--adcp
branch
from
e3d3dff to
030d59c
Compare
bokelley
changed the title
![aao-ipr-bot[bot]](https://avatars.githubusercontent.com/u/134922?s=60&v=4){kind=small}
There was a problem hiding this comment.
Clean release cut. Version stamp agrees across all three surfaces and the beta.10 skip is deliberate, not a dropped entry.
Things I checked
- Three files move in lockstep:
.release-please-manifest.json6.3.0-beta.10 → 6.3.0,pyproject.toml6.3.0b10 → 6.3.0(valid PEP 440),CHANGELOG.mdheader6.3.0. No version drift between the manifest, the package metadata, and the changelog. - No source touched — nothing under
src/adcp/in the diff, so no public-API surface, discriminated-union, or type-layering exposure. Skip-everything per the release-PR rule. - Compare link
v6.3.0-beta.9...v6.3.0intentionally jumps the unpublished6.3.0-beta.10manifest entry, matching the PR body: main carried an unpublished beta.10 while beta.9 is the latest published prerelease. Thepin AdCP 3.1 stablefix line carries forward into the stable entry rather than being lost. chore(main): releaseprefix is the correct conventional-commit semver signal for a release PR — no behavior change, no!warranted.
Minor nits (non-blocking)
- Hand-corrected release-please output. This is release-please's draft amended to stable because of the stranded beta.10 manifest entry. Worth confirming the next automated run reconciles cleanly against
6.3.0so the bot doesn't try to re-propose beta.10 — but that's a next-cycle concern, not this PR's.
LGTM. Approving via comment — GitHub blocks self-approval since the review identity owns this PR.
bokelley
left a comment
bokelley
left a comment
There was a problem hiding this comment.
Release PR corrected to stable 6.3.0; CI is green.
|
🤖 Created releases: 🌻 |
|
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final This is an automated message from the Argus AI review workflow. |
1 participant
🤖 I have created a release beep boop
6.3.0 (2026-06-18)
Features
Bug Fixes
This PR was generated with Release Please, then corrected to stable 6.3.0 because main already carried an unpublished 6.3.0-beta.10 manifest entry while the latest published prerelease is 6.3.0-beta.9.